View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001816 | T99X171.00 SKB Eagle | SW Issue | public | 2023-10-13 12:54 | 2025-04-07 10:05 |
| Reporter | (ALTech) Younkwang Jung | Assigned To | (SW) Willin Deng | Due Date | 2023-10-19 13:49 |
| Priority | normal | Severity | s4-minor | Reproducibility | N/A |
| Status | closed | Resolution | not a bug | ||
| Summary | 0001816: [Smart3][UI537] Request for VoC log analysis for RCU issue | ||||
| Description | Hi Jason Recently, more than 20k UI537 have been deployed in the field. And no input signal and RCU issue have been reported significantly https://jira.skbroadband.com/browse/BTVV-6868 Please analyze the attached logs for the two RCU VoCs and give us your opinion - 28:cd:c4:fc:33:62 If you look at the log, you can see the log where BT disconnects and then connects as shown below. Please give me your opinion on why you see this phenomenon. [Thu Sep 21 07:16:05 2023] atvr_remove: hdev->name = BRM_BA02_1DA removed, num 1->0 [Thu Sep 21 07:16:18 2023] atvr_probe: remotes count 0->1 [Thu Sep 21 07:18:07 2023] atvr_remove: hdev->name = BRM_BA02_1DA removed, num 1->0 [Thu Sep 21 07:18:20 2023] atvr_probe: remotes count 0->1 [Thu Sep 21 07:19:34 2023] atvr_remove: hdev->name = BRM_BA02_1DA removed, num 1->0 - 1c:bf:c0:12:52:e8 user tried paring, but the pairing continued to fail. please check the log 09-26 19:12:51.351 ToastUtil: showLitePopup() called. descMain : 리모컨 연결 중, descSub : , duration : 3000 09-26 19:12:51.352 ToastUtil: hideLitePopup() called 09-26 19:12:52.097 ToastUtil: showLitePopup() called. descMain : 리모컨 [BRM_BA01_14E] 연결 완료, descSub : , duration : 3000 Thank you YK.Jung | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| User List |
(ALTech) JunGyu Kim , (ALTech) SY Yoon |
|---|
|
|
|
|
|
Hi YK, I've checked your log. - 28:cd:c4:fc:33:62 I didn't see the corresponding logcat with your dmesg, I can't find any disconnect related logs in logcat either. e.g. android.bluetooth.device.action.ACL_DISCONNECTED - 1c:bf:c0:12:52:e8 It looks like the ad2p of BA01 RCU not paired correctly. the expected logs are as follow, but I can not find it in your logcat D AudioHAL:AudioHardwareInput: AudioHardwareInput::onDeviceFound hidraw flag = 0 D AudioHAL:AudioHardwareInput: AudioHardwareInput::onDeviceFound saving as device #0 I AS.AudioService: onAccessoryPlugMediaUnmute newDevice=128 [bt_a2dp] As you know, if the a2dp pairing fail the dpad will also disconnect. Thanks, Jason |
|
|
Hi Jason - 28:cd:c4:fc:33:62 Is it impossible to analyze if there is a log in dmesg.txt and there is no log in logcat? If this status is observed, you should add logs to the kernel as well. - 1c:bf:c0:12:52:e8 why is this issue observed ? , please give me your opinion And I requested to collect this STB. Thank you YK.Jung |
|
|
Hi YK, >>If this status is observed, you should add logs to the kernel as well. the demsg is the result, but we want to check the cause in logcat. Adding kernel log is not useful to us, based on the past experience, the BT vendor always ask us to provide the logcat/btsnoop, they rarely ask us to provide kernel log. the current situation is the SKB didn't collect the correct logcat around [Sep 21 07], so we can not see any disconnect related logs. >>why is this issue observed ? , please give me your opinion Did user see the code 33 or code 14 on screen? I checked the RCU type of log, and I compared the success log with user's logs. I found that user's RCU is BA01. but I didn't see that that a2dp was paired, this is my suspicion. As far as we know, if the a2dp pairing fail the the DPAD will also disconnect. Thanks, Jason |
|
|
Hi Jason Please analyze the two logs below 1) VoC logs show RCU connecting and disconnecting , 40_5B_D8_AD_62_22_20231015133637.zip The logcat log has alos been collected [Sun Oct 15 13:35:29 2023] atvr_remove: hdev->name = BRM_BA01_EA4 removed, num 1->0 [Sun Oct 15 13:35:29 2023] atvr_probe: remotes count 0->1 [Sun Oct 15 13:35:52 2023] atvr_remove: hdev->name = BRM_BA01_EA4 removed, num 1->0 [Sun Oct 15 13:35:52 2023] atvr_probe: remotes count 0->1 [Sun Oct 15 13:36:10 2023] atvr_remove: hdev->name = BRM_BA01_EA4 removed, num 1->0 [Sun Oct 15 13:36:12 2023] atvr_probe: remotes count 0->1 Please check it why this issue is observed 2) Nugu function is not working , B4_B5_B6_FF_86_BC_20231017104131.zip when I check the log , I suspect the following 10-17 10:37:34.181 I 3791 3999 WindowManager: interceptKeyTi keyCode=396 down=true repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=39 mSource=1793 mScanCode=194 mCharacters=null 10-17 10:37:34.182 E 3791 3999 WindowManager: interceptSkbFuctionKeyBeforeDispatching KEYCODE_SKB_FUNC_12 persist.sys.disable_nugu : .. 10-17 10:37:34.264 W 3531 7392 ServiceManager: Permission failure: android.permission.CAPTURE_AUDIO_OUTPUT from uid=10024 pid=11739 10-17 10:37:34.271 I 3461 3461 audio_hw_primary: adev_open_input_stream: use RC audio HAL 10-17 10:37:34.272 I 3461 3461 AudioHAL:AudioHardwareInput: openInputStream: ++ The nugu button has been pressed , but it doesn't seem to actually work. Please check it Thank you YK.Jung |
|
|
Hi YK, >>1) VoC logs show RCU connecting and disconnecting , 40_5B_D8_AD_62_22_20231015133637.zip Please check it with SPTEK, I suspect both SPTEK(iset)/UEI(quicket) send commands to RCU at the same time. (because I saw the Sptek (iset) log during paring BA01 RCU) As far as I know, if the paring RCU is BA01, SPTEK (iset) should ignore it. >>2)Nugu function is not working , B4_B5_B6_FF_86_BC_20231017104131.zip I reproduce it on our side, I also see the the following log in first press. ServiceManager: Permission failure: android.permission.CAPTURE_AUDIO_OUTPUT from uid=10024 pid=11739 then I press nugu button again, the nugu can recognize my speech, but the nugu didn't pop the "search result" Can you check what the word "not working" is? 1. The recognition panel does not pop up 2. nugu can not recognize user speech 3. can not pop the search result I see the case 3 on my side. Thanks, Jason |
|
|
no activity for this issue |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-10-13 12:54 | (ALTech) Younkwang Jung | New Issue | |
| 2023-10-13 12:54 | (ALTech) Younkwang Jung | Status | new => assigned |
| 2023-10-13 12:54 | (ALTech) Younkwang Jung | Assigned To | => (SW) Jason Ling |
| 2023-10-13 12:54 | (ALTech) Younkwang Jung | File Added: 28_CD_C4_FC_33_62_20230921135319.zip | |
| 2023-10-13 12:54 | (ALTech) Younkwang Jung | File Added: 1C_BF_C0_12_52_E8_20230926191313.zip | |
| 2023-10-13 12:55 | (ALTech) Younkwang Jung | Issue Monitored: (ALTech) SY Yoon | |
| 2023-10-13 12:55 | (ALTech) Younkwang Jung | Issue Monitored: (ALTech) JunGyu Kim | |
| 2023-10-16 19:13 |
|
Assigned To | (SW) Jason Ling => (ALTech) Younkwang Jung |
| 2023-10-16 19:13 |
|
Note Added: 0014324 | |
| 2023-10-17 08:07 | (ALTech) Younkwang Jung | Note Added: 0014325 | |
| 2023-10-17 08:38 |
|
Note Added: 0014326 | |
| 2023-10-19 10:39 | (ALTech) Younkwang Jung | Note Added: 0014345 | |
| 2023-10-19 10:39 | (ALTech) Younkwang Jung | File Added: 40_5B_D8_AD_62_22_20231015133637.zip | |
| 2023-10-19 10:39 | (ALTech) Younkwang Jung | File Added: B4_B5_B6_FF_86_BC_20231017104131.zip | |
| 2023-10-19 10:39 | (ALTech) Younkwang Jung | Due Date | 2023-10-16 13:49 => 2023-10-19 13:49 |
| 2023-10-20 18:39 |
|
Note Added: 0014366 | |
| 2025-04-07 10:05 | (SW) Kerwin Chen | Assigned To | (ALTech) Younkwang Jung => (SW) Willin Deng |
| 2025-04-07 10:05 | (SW) Kerwin Chen | Status | assigned => closed |
| 2025-04-07 10:05 | (SW) Kerwin Chen | Resolution | open => not a bug |
| 2025-04-07 10:05 | (SW) Kerwin Chen | Note Added: 0017429 |
